Page History: Resend Request
Compare Page Revisions
Page Revision: 2012/09/05 15:00
Message Range ReplayResend Request messages forces a response from the counterparty to acknowledge a continuation of FIX Session connectivity. Test requests can occur at any time during the FIX Session. When a test request is received, the party is obligated to respond to the Test Request message with a Heartbeat. Such heartbeat must also contain the TestRequestID (Tag 112) that originated in the original Test Request message.
Test Request messages also provide an opportunity to check for out-of-sequence conditions. It permits checking for the expected outgoing sequence number (Tag 34 of the Test Request) and expected incoming sequence number (Tag 34 of the mandatory hearbeat response).
The TestRequestID (Tag 112) can be text of any form. An unique string is recommended (e.g. an instantenous time label) to be able to pair Test Requests to their corresponding Hearbeat messages.
Message Dictionary| Tag | Field Name | Req'd | Comments |
|---|
| Standard Header | Y | MsgType = 2 |
| 7 | BeginSeqNo | N | Message sequence number of first message in range to be resent |
| 16 | EndSeqNo | N | Message sequence number of last message in range to be resent. If request is for a single message BeginSeqNo = EndSeqNo. If request is for all messages subsequent to a particular message, EndSeqNo = "0" (representing infinity). |
| | Standard Trailer | Y |
Sample Messages
Resend Request:
34=568|49=test|56=T4Test|50=Ernesto|52=20120905-19:57:01.947|7=1|16=2|
[FIXRESENDREQUEST]
[MsgSeqNum] 34 = 568
[SenderCompID] 49 = test
[TargetCompID] 56 = T4Test
[SenderSubID] 50 = Ernesto
[SendingTime] 52 = 20120905-19:57:01.947
[BeginSeqNo] 7 = 1
[EndSeqNo] 16 = 2
FIX API Home Page.